Libfido2 workflow#179
Merged
Merged
Conversation
padelsbach
reviewed
Jun 17, 2025
JeremiahM37
force-pushed
the
libfido2
branch
2 times, most recently
from
21c571e to
8b944a1
Compare
padelsbach
reviewed
Jun 17, 2025
JeremiahM37
force-pushed
the
libfido2
branch
5 times, most recently
from
4b2d78c to
e0d053f
Compare
padelsbach
reviewed
Jun 18, 2025
padelsbach
reviewed
Jun 18, 2025
JeremiahM37
force-pushed
the
libfido2
branch
2 times, most recently
from
dc5b06f to
4521014
Compare
padelsbach
approved these changes
Jun 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added yaml workflow for libfido2. All checks pass and it seems to work with wolfProvider as expected.
I did exclude one test, regress_dev, because it tests libfido2's ability to communicate with physical FIDO devices, which fails due to environmental factors. I don't think it will impact libfido2's core cryptographic functionality or its integration with wolfProvider as all other test pass and WOLFPROV_FORCE_FAIL=1 still causes most of the other tests to fail as it should.